Dynamic modification of a verification method associated with a transaction card

ABSTRACT

A device may determine that a verification method associated with a transaction card is to be modified from a first verification method to a second verification method. The first verification method and the second verification method may use different types of verification information. The device may provide a set of instructions to the transaction card after determining that the verification method is to be modified. The set of instructions may cause the transaction card to modify the verification method from the first verification method to the second verification method. The device may provide information identifying a modification to the verification method to a transaction backend device to notify the transaction backend device that the verification method associated with the transaction card has been modified from the first verification method to the second verification method.

BACKGROUND

A transaction card may be associated with a technical standard foroperating and/or processing transactions. In addition, a transactioncard may store data on an integrated circuit and/or a magnetic strip.Further, the transaction card may be associated with a verificationmethod, such as a chip and personal identification number (PIN) methodor a chip and signature method. With the chip and PIN method, a user ofa transaction card may input a PIN (e.g., a multiple digit number) intoa transaction terminal to complete a transaction. With the chip andsignature method, a user of a transaction card may sign a receipt or asignature pad associated with a transaction terminal to complete atransaction.

SUMMARY

According to some possible implementations, a device may include one ormore memories, and one or more processors, communicatively coupled tothe one or more memories, to determine that a verification methodassociated with a transaction card is to be modified from a firstverification method to a second verification method. The firstverification method and the second verification method may use differenttypes of verification information. The one or more processors mayprovide a set of instructions to the transaction card after determiningthat the verification method is to be modified. The set of instructionsmay cause the transaction card to modify the verification method fromthe first verification method to the second verification method. The oneor more processors may provide information identifying a modification tothe verification method to a transaction backend device to notify thetransaction backend device that the verification method associated withthe transaction card has been modified from the first verificationmethod to the second verification method.

According to some possible implementations, a non-transitorycomputer-readable medium may store one or more instructions that, whenexecuted by one or more processors, cause the one or more processors todetermine that a verification method, used to verify transactions of atransaction card, is to be reconfigured from a first verification methodto a second verification method. The second verification method mayinclude a chip and personal identification number (PIN) method, or achip and signature method. The one or more instructions, when executedby the one or more processors, may cause the one or more processors toprovide a set of instructions to the transaction card to cause thetransaction card to reconfigure from the first verification method tothe second verification method. The set of instructions may be providedto the transaction card via a wireless connection between thetransaction card and a device associated with the transaction card, or atransaction backend device. The one or more instructions, when executedby the one or more processors, may cause the one or more processors toprovide information to the transaction backend device to notify thetransaction backend device that the verification method used to verifythe transactions of the transaction card has been reconfigured to thesecond verification method.

According to some possible implementations, a method may includedetermining, by a device, that a verification method, used to verify auser of a transaction card, is to be enabled or disabled based on atleast one of: transaction terminal information, indicating whether atransaction terminal is capable of using the verification method, ortransaction backend information, indicating whether the verificationmethod is capable of completing the transaction. The method may includeproviding, by the device, a set of instructions to the transaction cardafter determining that the verification method is to be enabled ordisabled. The set of instructions may cause the transaction card toenable or disable the verification method. The method may includeproviding, by the device, information to a transaction backend device tonotify the transaction backend device that the verification methodassociated with the transaction card has been enabled or disabled.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented;

FIG. 3 is a diagram of example components of one or more devices of FIG.2;

FIG. 4 is a flow chart of an example process for dynamic modification ofa verification method associated with a transaction card;

FIG. 5 is a diagram of an example implementation relating to the exampleprocess shown in FIG. 4;

FIG. 6 is a diagram of an example implementation relating to the exampleprocess shown in FIG. 4;

FIG. 7 is a diagram of an example implementation relating to the exampleprocess shown in FIG. 4; and

FIG. 8 is a diagram of an example implementation relating to the exampleprocess shown in FIG. 4.

DETAILED DESCRIPTION

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

A transaction card may be configured to use a particular verificationmethod, such as a chip and personal identification number (PIN) methodor a chip and signature method. A user of the transaction card may wantto toggle the transaction card between various verification methods. Forexample, a user of a transaction card may want to modify the transactioncard from one verification method to another verification method whentravelling to a particular geographic location, based on a userpreference, and/or the like. Some transaction cards may not permit auser to toggle between verification methods. In addition, differentverification methods may use different communication protocols. This mayprevent a transaction card that uses one verification method from beingable to properly transfer information in a different geographiclocation, such as with a transaction terminal using a differentcommunication protocol, and/or the like that is associated with anotherverification method.

Some implementations, described herein, provide a user device that iscapable of permitting a user to modify a transaction card from using oneverification method to using another verification method via a wirelessconnection between the user device and the transaction card. In thisway, the user device permits quick and easy re-configuration of thetransaction card. This increases an efficiency of modifying theverification method that a transaction card uses by reducing oreliminating a need for a user to contact an organization associated withthe transaction card and/or by reducing or eliminating a need for theuser to obtain a replacement transaction card that uses a particularverification method. In addition, this conserves network resourcesand/or computing resources that would otherwise be consumed by providingthe user with a new transaction card that uses a particular verificationmethod. Further, this reduces or eliminates issues associated with usinga transaction card in different locations, with different merchants,and/or the like that use different verification methods (e.g., issuesassociated with a rejected transaction, a locked account, etc.).

FIG. 1 is a diagram of an overview of an example implementation 100described herein. As shown in FIG. 1, example implementation 100 mayinclude a transaction card, a user device, and a transaction backenddevice.

As shown in FIG. 1, and by reference number 110, the user device maydetermine that a verification method associated with a transaction cardis to be modified. For example, the user device may determine that averification method associated with the transaction card is to bemodified based on input from a user of the user device, based ondetecting a geographic location of the transaction card and/or the userdevice, based on a user preference of a user associated with the userdevice and/or the transaction card, based on a particular time of day orday of the week, based on a quantity of people that can use thetransaction card (e.g., when multiple people associated with anorganization have access to the transaction card), and/or the like.

The user device may determine a verification method to configure thetransaction card to use, a verification method to disable or enable,and/or the like. For example, the user device may determine averification method to use based on input from a user of the userdevice, using a data structure (e.g., to look up a verification methodto use), based on a verification method that the transaction card iscurrently using, based on a verification method used by a transactionterminal to which the transaction card is connected, and/or the like.

As shown by reference number 120, the user device may provide a set ofinstructions to the transaction card to cause the transaction card tomodify the verification method that the transaction card is using. Forexample, the set of instructions may cause the transaction card toconfigure to use a particular verification method, to enable aparticular verification method, to disable a particular verificationmethod, and/or the like. The user device may provide the set ofinstructions after determining the verification method to configure thetransaction card to use.

After receiving the set of instructions, the transaction card mayconfigure to use the verification method, may enable or disable averification method, and/or the like. In addition, the transaction cardmay verify that the transaction card can use the verification methodand/or that the transaction card is to modify the verification method(e.g., by communicating with the user device via a wireless connectionto request confirmation of the modification, by communicating with thetransaction backend device to confirm that the transaction card ispermitted to use the verification method, etc.). For example, thetransaction card may send a message to the user device for display(e.g., via a wireless connection between the transaction card and theuser device) to request confirmation of the modification, maycommunicate with the transaction backend device to confirm that a useraccount associated with the transaction card has been configured tosupport the verification method (e.g., that a user has configured a PINfor use with a chip and PIN configuration method, that a user hasconfigured biometric information for use with a biometric verificationmethod, etc.), and/or the like.

This conserves computing resources of the transaction card and/or thetransaction backend device by reducing or eliminating erroneousconfigurations of verification methods and/or by reducing or eliminatingissues (e.g., rejected transactions, locked accounts, etc.) that wouldoccur due to the transaction card, a transaction terminal, and/or thetransaction backend device attempting to use a verification method thatis not permitted.

As shown by reference number 130, the user device may provideinformation to notify a transaction backend device that the verificationmethod associated with the transaction card has been modified. Inaddition, the user device may provide information to identify theverification method that the transaction card was configured to use. Forexample, the user device may provide the information to the transactionbackend device after receiving a message from the transaction cardindicating that the verification method was successfully modified. Thisconserves processing resources of a transaction backend device and/or atransaction terminal by reducing or eliminating errors associated with amismatch between a verification method configured on a transaction cardand information stored by the transaction backend device that identifiesthe verification method that the transaction card is configured to use.

In this way, a user device permits quick and easy configuration of averification method for a transaction card by permitting a user to usethe user device to communicate with the transaction card to modify theverification method. This increases an efficiency of re-configuring atransaction card to use a different verification method. In addition,this conserves network resources and/or computing resources that wouldotherwise be consumed by modifying the verification method in a lessefficient manner, such as by contacting an organization to modify averification method. Further, this reduces or eliminates issuesassociated with using a transaction card in different locations, withdifferent merchants, and/or the like that use different verificationmethods, thereby conserving computing resources of devices associatedwith completing a transaction that would otherwise be consumed due to amismatch between a verification method associated with the transactioncard and a particular location, a particular merchant, and/or the like.

As indicated above, FIG. 1 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 1.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.2, environment 200 may include a user device 210, a transaction card220, a transaction backend device 230, a transaction terminal 240, and anetwork 250. Devices of environment 200 may interconnect via wiredconnections, wireless connections, or a combination of wired andwireless connections.

User device 210 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith modifying a verification method that transaction card 220 uses. Forexample, user device 210 may include a mobile phone (e.g., a smartphone, a radiotelephone, etc.), a laptop computer, a tablet computer, ahandheld computer, a gaming device, a wearable communication device(e.g., a smart wristwatch, a pair of smart eyeglasses, etc.), or asimilar type of device. In some implementations, user device 210 maydetermine to modify a verification method that transaction card 220uses, as described elsewhere herein. Additionally, or alternatively,user device 210 may provide a set of instructions to transaction card220 to cause transaction card 220 to use a particular verificationmethod, as described elsewhere herein.

Transaction card 220 includes a transaction card that can be used tocomplete a transaction. For example, transaction card 220 may include acredit card, a debit card, a gift card, a payment card, an automatedteller machine (ATM) card, a stored-value card, a fleet card, and/or thelike. Transaction card 220 may be capable of storing and/orcommunicating data for a point-of-sale (PoS) transaction withtransaction terminal 240. For example, transaction card 220 may storeand/or communicate data, including account information (e.g., an accountidentifier, a cardholder identifier, etc.), expiration information oftransaction card 220 (e.g., information identifying an expiration monthand/or year of transaction card 220), banking information (e.g., arouting number of a bank, a bank identifier, etc.), transactioninformation (e.g., a payment token), and/or the like. For example, tostore and/or communicate the data, transaction card 220 may include amagnetic strip and/or an integrated circuit (IC) chip (e.g., a EUROPAY®,MASTERCARD®, VISA® (EMV) chip).

Transaction card 220 may include an antenna to communicate dataassociated with transaction card 220. The antenna may be a passive radiofrequency (RF) antenna, an active RF antenna, and/or a battery-assistedRF antenna. In some implementations, transaction card 220 may be a smarttransaction card, capable of communicating wirelessly (e.g., viaBluetooth, Bluetooth Low Energy (BLE), near-field communication (NFC),and/or the like) with a computing device, such as user device 210, adigital wallet, and/or another device. In some implementations,transaction card 220 may receive a set of instructions from user device210 to modify a verification method that transaction card 220 is using,as described elsewhere herein. Additionally, or alternatively,transaction card 220 may modify a verification method that transactioncard 220 is using based on the set of instructions, as describedelsewhere herein.

Transaction backend device 230 includes one or more devices capable ofauthorizing and/or facilitating a transaction. For example, transactionbackend device 230 may include one or more servers and/or computers tostore and/or provide information associated with processing atransaction via transaction terminal 240. In some implementations,transaction backend device 230 may store information that identifies averification method associated with transaction card 220, as describedelsewhere herein. Additionally, or alternatively, transaction backenddevice 230 may provide a set of instructions to transaction card 220 tomodify a verification method that transaction card 220 is using, asdescribed elsewhere herein.

Transaction backend device 230 may include one or more devicesassociated with a financial institution (e.g., a bank, a lender, acredit union, etc.) and/or a transaction card association thatauthorizes a transaction and/or facilitates a transfer of funds orpayment between an account associated with a cardholder of transactioncard 220 and an account of an individual or business associated withtransaction terminal 240. For example, transaction backend device 230may include one or more devices of one or more issuing banks associatedwith a cardholder of transaction card 220, one or more devices of one ormore acquiring banks (or merchant banks) associated with transactionterminal 240, and/or one or more devices associated with one or moretransaction card associations (e.g., VISA®, MASTERCARD®, and/or thelike) associated with transaction card 220. Accordingly, based onreceiving information associated with transaction card 220 fromtransaction terminal 240, devices of transaction backend device 230(e.g., associated with a financial institution or transaction cardassociation) may communicate to authorize a transaction and/or transferfunds between the accounts associated with transaction card 220 and/ortransaction terminal 240.

Transaction backend device 230 may provide or deny authorizationassociated with a transaction. For example, transaction backend device230 may store and/or provide information that may allow, or deny, accessthrough an access point (e.g., a gate, a door, and/or the like) of asecure location (e.g., a room, a building, a geographical area, atransportation terminal, and/or the like) based on information (e.g.,account information, a key, an identifier, credentials, and/or the like)associated with transaction card 220 and/or provided by transactionterminal 240.

Transaction backend device 230 may include one or more devicesassociated with a rewards program associated with transaction card 220and/or an entity (e.g., a financial institution, a merchant, a serviceprovider, a vendor, and/or the like) associated with transaction card220 and/or transaction terminal 240. For example, transaction backenddevice 230 may authorize the earning and/or redemption of rewards (e.g.,rewards points associated with transaction card 220, cash rewards,client loyalty rewards associated with an entity associated withtransaction terminal 240, and/or the like) based on a transactionprocessed by transaction terminal 240.

Transaction terminal 240 includes one or more devices capable offacilitating processing of a transaction associated with transactioncard 220. For example, transaction terminal 240 may include a PoSterminal, a payment terminal (e.g., a credit card terminal, acontactless payment terminal, a mobile credit card reader, a chipreader, etc.), a security access terminal, an ATM terminal, and/or thelike. In some implementations, transaction terminal 240 may detect averification method that transaction card 220 is configured to use andmay determine whether transaction card 220 is configured to use the sameverification method as transaction terminal 240, as described elsewhereherein. Additionally, or alternatively, transaction terminal 240 mayprovide a message to transaction backend device 230 that transactioncard 220 is configured to use a different verification method thantransaction terminal 240, as described elsewhere herein.

In some implementations, transaction terminal 240 may include one ormore input components and/or output components to facilitate obtaininginformation from transaction card 220 (e.g., an account number of anaccount associated with transaction card 220, an expiration date oftransaction card 220, etc.), input (e.g., a PIN, a signature, biometricinformation, etc.), from a cardholder of transaction card 220, relatedto completing and/or authorizing a transaction, and/or the like. In someimplementations, example input components of transaction terminal 240may include a number keypad, a touchscreen, a magnetic strip reader, achip reader, a pen and corresponding signature pad, an RF signal reader,and/or the like.

In some implementations, a magnetic strip reader of transaction terminal240 may receive data from transaction card 220 as a magnetic strip oftransaction card 220 is swiped along the magnetic strip reader. In someimplementations, a chip reader of transaction terminal 240 may receivedata from transaction card 220 via an integrated circuit chip (e.g., anEMV chip) of transaction card 220 when the chip is placed withincommunicative proximity of the chip reader. In some implementations, anRF signal reader of transaction terminal 240 may enable a contactlesstransaction from transaction card 220 by obtaining data wirelessly fromtransaction card 220 as transaction card 220 comes within communicativeproximity of transaction terminal 240, such that the RF signal readerdetects an RF signal from an RF antenna of transaction card 220.

In some implementations, example output components of transactionterminal 240 may include a display, a speaker, a printer, a light,and/or the like. In some implementations, transaction terminal 240 mayuse an output component to output information related to a transaction(e.g., an indication to cause a user to input information to authorize atransaction, information that identifies whether a transaction wascompleted, etc.).

Network 250 includes one or more wired and/or wireless networks. Forexample, network 250 may include a cellular network (e.g., a long-termevolution (LTE) network, a code division multiple access (CDMA) network,a 3G network, a 4G network, a 5G network, another type of cellularnetwork, etc.), a public land mobile network (PLMN), a local areanetwork (LAN), a wide area network (WAN), a metropolitan area network(MAN), a telephone network (e.g., the Public Switched Telephone Network(PSTN)), a private network, an ad hoc network, an intranet, theInternet, a fiber optic-based network, a cloud computing network, or thelike, and/or a combination of these or other types of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to user device 210, transaction card 220, transactionbackend device 230, and/or transaction terminal 240. In someimplementations, user device 210, transaction card 220, transactionbackend device 230, and/or transaction terminal 240 may include one ormore devices 300 and/or one or more components of device 300. As shownin FIG. 3, device 300 may include a bus 310, a processor 320, a memory330, a storage component 340, an input component 350, an outputcomponent 360, and a communication interface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320includes a central processing unit (CPU), a graphics processing unit(GPU), an accelerated processing unit (APU), a microprocessor, amicrocontroller, a digital signal processor (DSP), a field-programmablegate array (FPGA), an application-specific integrated circuit (ASIC), oranother type of processing component. In some implementations, processor320 includes one or more processors capable of being programmed toperform a function. Memory 330 includes a random access memory (RAM), aread only memory (ROM), and/or another type of dynamic or static storagedevice (e.g., a flash memory, a magnetic memory, and/or an opticalmemory) that stores information and/or instructions for use by processor320.

Storage component 340 stores information and/or software related to theoperations and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for dynamicmodification of a verification method associated with a transactioncard. In some implementations, one or more process blocks of FIG. 4 maybe performed by user device 210. In some implementations, one or moreprocess blocks of FIG. 4 may be performed by another device or a groupof devices separate from or including user device 210, such astransaction card 220, transaction backend device 230, and transactionterminal 240.

As shown in FIG. 4, process 400 may include determining that averification method associated with a transaction card is to be modified(block 410). For example, user device 210 may determine that averification method associated with transaction card 220 is to bemodified.

In some implementations, a verification method may include a techniquethat is used to determine whether a user of transaction card 220 is alegitimate cardholder of transaction card 220. For example, averification method may include a chip and PIN method, a chip andsignature method, a biometric authentication method where, for example,biometric information (e.g., information that identifies a finger print,facial geometry, a retina and/or iris pattern, a deoxyribonucleic acid(DNA) sequence, etc.) is used to determine whether a user of transactioncard 220 is a legitimate cardholder of transaction card 220, noverification method or a verification method that does not need input ofinformation to authenticate a transaction, and/or the like. In someimplementations, a verification method may be associated with aparticular communication protocol that is used to provide informationrelated to a transaction (e.g., to transaction backend device 230,transaction terminal 240, etc.). In some implementations, differentverification methods may use different communication protocols.

In some implementations, user device 210 may determine that averification method associated with transaction card 220 is to bemodified based on input from a user of user device 210. For example,user device 210 may receive input from a user of user device 210 thatindicates that a verification method associated with transaction card220 is to be modified.

Additionally, or alternatively, user device 210 may determine that averification method associated with transaction card 220 is to bemodified based on a geographic location of user device 210 and/ortransaction card 220 (e.g., when different verification methods areassociated with different geographic locations). For example, userdevice 210 may detect a geographic location of user device 210 and/ortransaction card 220 and may determine that a verification methodassociated with transaction card 220 is to be modified based on thegeographic location.

Continuing with the previous example, user device 210 may determine thatuser device 210 and/or transaction card 220 is in a particulargeographic location using a GPS component of user device 210 and/ordetermining that user device 210 is in communicative proximity oftransaction card 220 (e.g., user device 210 and transaction card 220being within communicative proximity may indicate that user device 210and transaction card 220 are in the same geographic location). Asanother example, user device 210 may receive information identifying alocation (e.g., a geographic location, a merchant location, etc.) ofuser device 210 and/or transaction card 220 and may identify averification method to configure transaction card 220 to use based onthe location of user device 210 and/or transaction card 220.

Additionally, or alternatively, user device 210 may determine that averification method associated with transaction card 220 is to bemodified based on receiving information from transaction card 220 and/ortransaction backend device 230 that indicates that the verificationmethod associated with transaction card 220 is different than averification method associated with transaction terminal 240. Forexample, when transaction card 220 is within communicative proximity oftransaction terminal 240, user device 210 may receive, from transactionbackend device 230 and/or transaction terminal 240 (e.g., viatransaction card 220), transaction terminal information that indicates averification method associated with transaction terminal 240 (e.g., averification method that transaction terminal 240 is capable of using),that a verification method associated with transaction card 220 does notmatch a verification method associated with transaction terminal 240,and/or the like.

Additionally, or alternatively, and as another example, user device 210may determine that a verification method associated with transactioncard 220 is to be modified based on transaction backend information. Forexample, transaction backend information may indicate whether theverification method associated with transaction card 220 is capable ofcompleting a transaction for which transaction card 220 is being used.

In some implementations, user device 210 may determine that averification method associated with transaction card 220 is to bemodified based on receiving a request from transaction card 220. Forexample, user device 210 may receive, from transaction card 220, arequest to modify a verification method associated with transaction card220 after transaction card 220 is communicatively coupled to transactionterminal 240 and transaction card 220 and/or transaction terminal 240determines that the verification method associated with transaction card220 needs to be modified.

Additionally, or alternatively, user device 210 may determine that averification method associated with transaction card 220 is to bemodified based on a preference. For example, user device 210 maydetermine that a verification method associated with transaction card220 is to be modified based on a user preference associated with a userof user device 210 and/or transaction card 220 (e.g., associated with anaccount associated with user device 210 and/or transaction card 220), apreference of a merchant with which transaction card 220 is being usedto complete a transaction (e.g., associated with a merchant accountassociated with transaction terminal 240), and/or the like. Continuingwith the previous example, if multiple individuals have permission touse transaction card 220, user device 210 may determine a userpreference for a verification method when user device 210 detects thattransaction card 220 is within communicative proximity of user device210 (e.g., indicating that a user of user device 210 is to be a user oftransaction card 220).

Additionally, or alternatively, user device 210 may determine to modifya verification method associated with transaction card 220 based on aparticular day of the week, time of the day, and/or the like. Forexample, a user of user device 210 may use an electronic calendarassociated with user device 210 to set a schedule for use of aparticular verification method (e.g., for when the user is going to betravelling to a different geographic location) and user device 210 maydetermine to modify a verification method associated with transactioncard 220 during the scheduled time period.

Additionally, or alternatively, user device 210 may determine to modifya verification method based on information indicating that an accountassociated with user device 210 and/or transaction card 220 haspermission to modify the verification method. For example, user device210 may receive information from transaction card 220 and/or transactionbackend device 230 that indicates whether an account associated withuser device 210 has permission to modify a verification methodassociated with transaction card 220.

Additionally, or alternatively, user device 210 may determine that averification method associated with transaction card 220 is to bemodified based on a purchase amount associated with a transaction (e.g.,where the purchase amount satisfies a threshold). For example, a firstthreshold purchase amount may correspond to a first verification methodand a second threshold purchase amount may correspond to a secondverification method. Additionally, or alternatively, user device 210 maydetermine that a verification method associated with transaction card220 is to be modified based on a type of merchant. For example,different verification methods may be associated with different types ofmerchants, such as a gas station, a retailer, a restaurant, a serviceprovider, and/or the like.

Additionally, or alternatively, user device 210 may determine that averification method associated with transaction card 220 is to bemodified based on a type of transaction being completed. For example,different types of verification methods may be associated with differenttypes of transactions, such as a cash back transaction, a cashwithdrawal, a credit transaction, a debit transaction, and/or the like.Additionally, or alternatively, user device 210 may determine that averification method associated with transaction card 220 is to bemodified based on a quantity of transactions during a time period (e.g.,based on the quantity of transactions satisfying a threshold).Additionally, or alternatively, user device 210 may determine that averification method associated with transaction card 220 is to bemodified such that the verification method associated with transactioncard 220 matches the highest security verification method associatedwith transaction terminal 240 relative to other verification methods.

In some implementations, user device 210 may determine whether amodification to a verification method is approved. For example, userdevice 210 may request confirmation of the modification from a user ofuser device 210, may request that a user input authenticationinformation (e.g., a PIN, a username and password combination, biometricinformation, etc.) to approve the modification, and/or the like, and maydetermine to modify the verification method based on the input.

In some implementations, user device 210 may determine whethertransaction card 220 can use a particular verification method. Forexample, user device 210 may communicate with transaction card 220and/or transaction backend device 230 to determine whether transactioncard 220 can use a particular verification method and may determine tomodify the verification method based on determining that transactioncard 220 can use the particular verification method. This conservescomputing resources that would otherwise be used to attempt to configuretransaction card 220 to use a particular verification method thattransaction card 220 cannot use.

In some implementations, user device 210 may determine a verificationmethod to configure transaction card 220 to use by performing a lookupin a data structure. For example, user device 210 may perform a lookupof information that identifies a geographic location of user device 210and/or transaction card 220, a user preference of a user device 210and/or transaction card 220 (e.g., where a user preference prioritizesone verification method over another), a particular day of the week ortime of the day, and/or the like and may identify a correspondingverification method when a result of the lookup indicates a match.

In some implementations, user device 210 may determine to modify averification method when transaction card 220 is local to user device210. For example, user device 210 may determine to modify a verificationmethod when transaction card 220 is within communicative proximity ofuser device 210, is connected wirelessly to user device 210, isconnected to a transaction terminal 240 that is at the same geographiclocation as user device 210, and/or the like. In some implementations,user device 210 may determine to communicate with transaction card 220via a wireless connection between transaction card 220 and user device210 when transaction card 220 is local to user device 210 (e.g., mayprovide a set of instructions, described elsewhere herein, totransaction card 220 via a wireless connection).

Additionally, or alternatively, user device 210 may determine to modifya verification method when transaction card 220 is remote to user device210. For example, user device 210 may determine to modify a verificationmethod when transaction card 220 is not within communicative proximityof user device 210, is not wirelessly connected to user device 210,and/or the like (e.g., when user device 210 is associated with a parentor an organization and transaction card 220 is associated with a childor an employee and the child or employee has traveled to a differentgeographic location than the parent or organization). In someimplementations, user device 210 may determine to communicate withtransaction card 220 via transaction backend device 230 when transactioncard 220 is remote to user device 210 (e.g., may provide a set ofinstructions, described elsewhere herein, to transaction card 220 viatransaction backend device 230).

In this way, user device 210 may determine to modify a verificationmethod associated with transaction card 220 prior to user device 210providing a set of instructions to transaction card 220 to modify theverification method.

As further shown in FIG. 4, process 400 may include providing a set ofinstructions to the transaction card to cause the transaction card tomodify the verification method (block 420). For example, user device 210may provide a set of instructions to transaction card 220 to modify theverification method. In some implementations, user device 210 mayprovide the set of instructions after determining to modify theverification method, after determining a verification method toconfigure transaction card 220 to use, based on user input from a userof user device 210 (e.g., based on input confirming modification of theverification method), via a wireless connection between user device 210and transaction card 220, and/or the like. In some implementations,transaction card 220 may automatically modify a verification methodassociated with transaction card 220 (e.g., without receiving a set ofinstructions from user device 210 to modify the verification method).

In some implementations, a set of instructions may cause transactioncard 220 to configure to use a verification method. For example, a setof instructions may cause transaction card 220 to configure from a firstverification method to a second verification method that is differentthan the first verification method (e.g., that uses a different type ofverification information). Additionally, or alternatively, a set ofinstructions may cause transaction card 220 to enable and/or disablevarious verification methods. For example, a set of instructions maycause transaction card 220 to enable a verification method, to disable averification method, to enable a first verification method and todisable a second verification method, and/or the like.

Additionally, or alternatively, a set of instructions may causetransaction card 220 to use a particular protocol. For example, a set ofinstructions may modify transaction card 220 from using a first protocolto using a second protocol. In some implementations, a set ofinstructions may modify a verification method that an IC chip associatedwith transaction card 220 uses (e.g., a protocol that the IC chip uses).

In some implementations, user device 210 may determine whether userdevice 210 and transaction card 220 are within communicative proximity(e.g., whether user device 210 and transaction card 220 are connectedwirelessly). In some implementations, user device 210 may determine toprovide a set of instructions to transaction card 220 via a wirelessconnection between user device 210 and transaction card 220 when userdevice 210 and transaction card 220 are within communicative proximity.This conserves network resources, such as bandwidth, by reducing oreliminating a need for user device 210 to provide the set ofinstructions via network 250. In some implementations, user device 210may prevent a set of instructions from being provided to transactioncard 220 until user device 210 and transaction card 220 are withincommunicative proximity. This conserves computing resources of userdevice 210 that would otherwise be consumed attempting to provide a setof instructions to transaction card 220 when user device 210 andtransaction card 220 are not within communicative proximity.

Additionally, or alternatively, user device 210 may determine to providea set of instructions to transaction card 220 via transaction backenddevice 230 when user device 210 and transaction card 220 are not withincommunicative proximity. This improves a capability of user device 210to provide a set of instructions to transaction card 220 by reducing oreliminating a need for user device 210 and transaction card 220 to bewithin communicative proximity.

In some implementations, user device 210 may provide a set ofinstructions to transaction card 220 after connecting to transactioncard 220 (e.g., when transaction card 220 is within communicativeproximity of user device 210). For example, a user of user device 210may select a particular transaction card 220 to which to provide a setof instructions and user device 210 may connect to the particulartransaction card 220 (e.g., using a security token, a password andusername combination, and/or the like input by a user of user device210, stored by user device 210, etc.) to permit user device 210 toprovide the set of instructions to transaction card 220.

In some implementations, user device 210 may provide information totransaction card 220 to authenticate the set of instructions and/or toauthorize the modification (e.g., authentication information). Forexample, user device 210 may provide a PIN input by a user of userdevice 210, information identifying a username and password combinationof an account associated with user device 210 and/or transaction card220, a security token, a key, and/or the like to transaction card 220 toauthenticate the set of instructions and/or to authorize themodification of the verification method. In some implementations, userdevice 210 may provide information to authenticate a set of instructionsand/or to authorize a modification to a verification method directly totransaction card 220 via a wireless connection between user device 210and transaction card 220. Additionally, or alternatively, user device210 may provide information to authenticate a set of instructions and/orto authorize a modification to a verification method via transactionbackend device 230.

Additionally, or alternatively, user device 210 may provide informationto verify a transaction for which transaction card 220 is being used(e.g., verification information), such as when user device 210 providesa set of instructions when transaction card 220 is connected totransaction terminal 240. For example, verification information mayinclude a PIN, a signature, biometric information, and/or the like.

In some implementations, transaction card 220 may provide a message touser device 210 to confirm modification of the verification, to notifyuser device 210 of a successful modification, and/or the like. Forexample, transaction card 220 may provide a message to user device 210directly when user device 210 and transaction card 220 are connectedwirelessly. Additionally, or alternatively, and as another example,transaction card 220 may provide a message to user device 210 viatransaction backend device 230 and transaction terminal 240 when userdevice 210 and transaction card 220 are not connected wirelessly.

In this way, user device 210 may provide a set of instructions totransaction card 220 prior to providing information to transactionbackend device 230 to notify transaction backend device 230 of themodification to the verification method.

As further shown in FIG. 4, process 400 may include providinginformation to notify a transaction backend device that the verificationmethod associated with the transaction card has been modified (block430). For example, user device 210 may provide information to notifytransaction backend device 230 that the verification method associatedwith transaction card 220 has been modified. In some implementations,user device 210 may provide the information to notify transactionbackend device 230 after providing a set of instructions to transactioncard 220, after receiving information confirming modification of theverification method from transaction card 220, based on input from auser of user device 210, and/or the like.

In some implementations, providing information to notify transactionbackend device 230 conserves processing resources of transaction card220, transaction backend device 230, and/or transaction terminal 240that would otherwise be consumed by erroneous processing of transactionsby permitting transaction backend device 230 to identify a manner inwhich to process a transaction and/or by permitting transaction backenddevice 230 to accurately identify a verification method associated withtransaction card 220. In addition, this improves fraud prevention bycausing transaction backend device 230 to properly process atransaction.

In some implementations, the information that user device 210 providesto transaction backend device 230 may identify the verification methodthat transaction card 220 was configured to use. Additionally, oralternatively, the information may include authentication information toauthorize transaction backend device 230 to modify informationidentifying the verification method associated with transaction card 220and/or verification information to permit transaction backend device 230to verify and/or authorize a transaction.

In some implementations, transaction card 220, rather than user device210, may provide information to transaction backend device 230 to notifytransaction backend device 230. For example, transaction card 220 mayprovide the information to transaction backend device 230 viatransaction terminal 240 when transaction card 220 is withincommunicative proximity of transaction terminal 240. This conservesprocessing resources of user device 210 by reducing or eliminating aneed for user device 210 to provide this information.

In some implementations, user device 210 may update a log with atimestamp that identifies a date, a time, and/or the like of themodification of the verification method. Additionally, or alternatively,user device 210 may provide a generated report for display (e.g., via adisplay of user device 210) that identifies information related to themodification. Additionally, or alternatively, user device 210 may send amessage to another user device 210 (e.g., associated with a primaryaccount with which transaction card 220 is associated) to notify aprimary account holder of the modification to the verification method.Additionally, or alternatively, user device 210 may store informationrelated to the modification (e.g., a geographic location, a transactiontype (e.g., a purchase, a transfer, charged against a line of credit,etc.), and/or the like to permit user device 210 to automatically modifythe verification method for future transactions.

In this way, user device 210 may provide information to notifytransaction backend device 230 that the verification method associatedwith transaction card 220 has been modified.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

FIG. 5 is a diagram of an example implementation 500 relating to exampleprocess 400 shown in FIG. 4. FIG. 5 shows an example of transaction card220 authenticating a set of instructions to modify a verification methodassociated with transaction card 220.

As shown in FIG. 5, and by reference number 510, transaction card 220may receive a set of instructions to modify a verification methodassociated with transaction card 220. For example, transaction card 220may receive the set of instructions after user device 210 determinesthat a verification method associated with transaction card 220 is to bemodified.

As shown by reference number 520, transaction card 220 may authenticatethe set of instructions to modify the verification method (e.g., priorto modifying the verification method). In some implementations,transaction card 220 may authenticate the set of instructions usingauthentication information (e.g., biometric information, a username andpassword combination, a PIN, etc.) from user device 210. For example,transaction card 220 may receive authentication information input by auser of user device 210, authentication information stored on userdevice 210, and/or the like.

In some implementations, transaction card 220 may perform a comparisonof authentication information to authenticate the set of instructions.For example, transaction card 220 may perform a comparison ofauthentication information received from user device 210 andauthentication information that transaction card 220 is storing and mayauthenticate the set of instructions when a result of the comparisonindicates a match. In some implementations, transaction card 220 mayauthenticate the set of instructions using transaction backend device230. For example, transaction card 220 may provide authenticationinformation received from user device 210 to transaction backend device230 (e.g., via transaction terminal 240) to permit transaction backenddevice 230 to authenticate the set of instructions. Conversely, and asanother example, user device 210 may provide the authenticationinformation to transaction backend device 230 and transaction backenddevice 230 may provide a notification to transaction card 220 (e.g., viatransaction terminal 240) that identifies whether the set ofinstructions is authenticated.

As shown by reference number 530, transaction card 220 may modify theverification method. For example, transaction card 220 may modify theverification method based on authenticating the set of instructions andin a manner similar to that described elsewhere herein. In someimplementations, transaction card 220 may determine whether averification method can be used prior to modifying the verificationmethod. For example, transaction card 220 may use information stored ontransaction card 220, may communicate with transaction backend device230 (e.g., via transaction terminal 240), and/or may communicate withtransaction terminal 240 to determine whether transaction card 220 canuse a particular verification method (e.g., based on a geographiclocation of transaction card 220 and/or user device 210, a preference ofan account associated with transaction card 220, and/or the like). Thisconserves processing resources of transaction card 220 that wouldotherwise be consumed attempting to configure transaction card 220 touse a verification method that transaction card 220 cannot use.

As shown by reference number 540, transaction card 220 may provideinformation to notify user device 210 of a successful modification ofthe verification method. For example, transaction card 220 may provideinformation for display that indicates a successful (or unsuccessful)modification of the verification method.

In this way, transaction card 220 may authenticate a set of instructionsto modify a verification method, thereby increasing a security oftransaction card 220 and/or conserving computing resources that wouldotherwise be consumed due to an erroneous modification of a verificationmethod.

As indicated above, FIG. 5 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 5.

FIG. 6 is a diagram of an example implementation 600 relating to exampleprocess 400 shown in FIG. 4. FIG. 6 shows an example of user device 210determining that a verification method associated with transaction card220 is to be modified based on a geographic location of user device 210.

As shown in FIG. 6, and by reference number 610, user device 210 maydetect that user device 210 is at a particular geographic location. Forexample, user device 210 may determine that user device 210 is at aparticular location based on information from a GPS component of userdevice 210 that identifies a GPS location of user device 210. In someimplementations, if user device 210 is connected to transaction card 220(e.g., wirelessly using Bluetooth or NFC), then user device 210 maydetermine that transaction card 220 is in the same geographic locationas user device 210. In some implementations, user device 210 maydetermine that a verification method of transaction card 220 is to bemodified based on the geographic location of user device 210. Forexample, different countries may use different verification methods tocomplete transactions and transaction card 220 may need to be configuredto use a particular verification method when being used at in aparticular country.

As shown by reference number 620, user device 210 may provide a set ofinstructions to transaction card 220 to cause transaction card 220 tomodify the verification method. For example, user device 210 may providea set of instructions similar to that described elsewhere herein. Asshown by reference number 630, transaction card 220 may modify theverification method in a manner similar to that described elsewhereherein (e.g., by configuring to use a particular verification method, byenabling or disabling various verification methods, etc.).

In some implementations, transaction card 220 may verify themodification (e.g., prior to modifying the verification method). Forexample, transaction card 220 may provide to user device 210, fordisplay, a message requesting confirmation of the modification from auser of user device 210, such as by requesting input from a user of userdevice 210 to approve or confirm a modification of a verificationmethod. In some implementations, transaction card 220 may determine thatthe verification method is to be modified based on receiving the inputfrom user device 210.

In some implementations, transaction card 220 may wait to modify theverification method until transaction card 220 is connected totransaction terminal 240. For example, this may permit transaction card220 to communicate with transaction terminal 240 and/or transactionbackend device 230 to confirm a geographic location of transaction card220, to confirm that transaction card 220 and/or transaction terminal240 can be configured to use a verification method, and/or the like. Insome implementations, transaction card 220 may provide information touser device 210 indicating that the verification method has beensuccessfully modified after modifying the verification method.

As shown by reference number 640, user device 210 may provideinformation to notify transaction backend device 230 that theverification method associated with transaction card 220 has beenmodified, in a manner similar to that described elsewhere herein. Forexample, the information may permit transaction backend device 230 toupdate a record associated with transaction card 220. As shown byreference number 650, transaction backend device 230 may update recordsto identify the verification method associated with transaction card220, in a manner similar to that described elsewhere herein. Forexample, transaction backend device 230 may update a data structure toidentify the verification method to which transaction card 220 wasconfigured.

In this way, user device 210 may determine that a verification methodassociated with transaction card 220 is to be modified based on ageographic location of user device 210.

As indicated above, FIG. 6 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 6.

FIG. 7 is a diagram of an example implementation 700 relating to exampleprocess 400 shown in FIG. 4. FIG. 7 shows an example of transaction card220 initiating modification of a verification method associated withtransaction card 220.

As shown in FIG. 7, and by reference number 710, transaction card 220may be connected to transaction terminal 240 (e.g., in association withcompleting a transaction via transaction terminal 240). For example, achip of transaction card 220 may be within communicative proximity of achip reader of transaction terminal 240 (e.g., a chip of transactioncard 220 may be inserted into a chip reader of transaction terminal240). As shown by reference number 720, transaction card 220 may detectthat transaction card 220 is at a particular geographic location. Forexample, transaction card 220 may receive, from transaction terminal 240and/or user device 210, information that identifies a geographiclocation of transaction terminal 240 and transaction card 220 may detectthat transaction card 220 is at a particular geographic location basedon this information.

As shown by reference number 730, transaction card 220 may modify averification method associated with transaction card 220, in a mannersimilar to that described elsewhere herein. In some implementations,transaction card 220 may determine a verification method to which toconfigure transaction card 220 based on information from transactionterminal 240 that identifies a verification method associated withtransaction terminal 240. Additionally, or alternatively, transactioncard 220 and/or transaction backend device 230 may perform a lookup todetermine the verification method to which transaction card 220 is toconfigure (e.g., using information that identifies a geographic locationof transaction card 220). In some implementations, transaction card 220may determine whether transaction card 220 can use the verificationmethod to which transaction card 220 is to configure (e.g., bydetermining whether an account associated with transaction card 220 canuse the verification method). Additionally, or alternatively,transaction card 220 may communicate with transaction backend device 230to determine whether transaction card 220 can use the verificationmethod (e.g., by requesting that transaction backend device 230 confirmwhether transaction card 220 can use the verification method).

As shown by reference number 740, transaction card 220 may provideinformation indicating that the verification method has been modified.For example, transaction card 220 may provide the information via userdevice 210. Additionally, or alternatively, transaction card 220 mayprovide the information via transaction terminal 240. As shown byreference number 750, transaction backend device 230 may update recordsto identify the verification method associated with transaction card220, in a manner similar to that described elsewhere herein. As shown byreference number 760, transaction backend device 230 may authorize atransaction for which transaction card 220 is being used. For example,transaction backend device 230 may request, via transaction terminal240, input of verification information (e.g., a signature, a PIN,biometric information, etc.) and may determine whether the verificationinformation input via transaction terminal 240 and information stored bytransaction backend device 230 match.

In this way, transaction card 220 may initiate modification of averification method associated with transaction card 220.

As indicated above, FIG. 7 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 7.

FIG. 8 is a diagram of an example implementation 800 relating to exampleprocess 400 shown in FIG. 4. FIG. 8 shows an example of transactionbackend device 230 determining that a verification method associatedwith transaction card 220 is to be modified.

As shown in FIG. 8, and by reference number 810, transaction card 220may be connected to transaction terminal 240, in a manner similar tothat described elsewhere herein (e.g., a chip of transaction card 220and a chip reader of transaction terminal 240 may be in communicativeproximity). As shown by reference number 820, transaction card 220 mayrequest authorization for a transaction. For example, transaction card220 may request, via transaction terminal 240, that transaction backenddevice 230 authorize a transaction. As shown by reference number 830,transaction backend device 230 may detect that transaction card 220 isat a particular geographic location. For example, transaction backenddevice 230 may detect that transaction card 220 is at a particulargeographic location based on information received from transactionterminal 240 and/or transaction card 220. In some implementations,transaction backend device 230 may determine that a verification methodassociated with transaction card 220 is to be modified based on theparticular geographic location at which transaction card 220 is located.

As shown by reference number 840, transaction backend device 230 mayrequest permission to modify a verification method associated withtransaction card 220 (e.g., from user device 210). For example,transaction backend device 230 may provide, for display, information touser device 210 that indicates that the verification method associatedwith transaction card 220 needs to be modified to complete thetransaction and may request confirmation of the modification. As shownby reference number 850, transaction backend device 230 may receiveinformation granting permission to modify the verification method (e.g.,from user device 210). In some implementations, transaction backenddevice 230 may receive authentication information from user device 210to permit transaction backend device 230 to confirm the modification.

As shown by reference number 860, transaction backend device 230 mayprovide a set of instructions to modify the verification methodassociated with transaction card 220. For example, transaction backenddevice 230 may provide, via transaction terminal 240, a set ofinstructions to cause transaction card 220 to modify a verificationmethod associated with transaction card 220. As shown by referencenumber 870, transaction card 220 may modify the verification methodassociated with transaction card 220, in a manner similar to thatdescribed elsewhere herein. As shown by reference number 880,transaction card 220 may provide information indicating that theverification method has been modified. For example, transaction card 220may provide information to user device 210 for display.

In this way, transaction backend device 230 may determine that averification method associated with transaction card 220 is to bemodified.

As indicated above, FIG. 8 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 8.

In this way, user device 210 permits quick and easy configuration of averification method for transaction card 220 by permitting a user to useuser device 210 to modify the verification method. This increases anefficiency of re-configuring transaction card 220 to use a differentverification method (e.g., to use a different protocol). In addition,this conserves network resources and/or computing resources that wouldotherwise be consumed modifying the verification method in a lessefficient manner, such as by contacting an organization to modify averification method. Further, this reduces or eliminates issuesassociated with using transaction card 220 in different locations, withdifferent merchants, and/or the like that use different verificationmethods, thereby conserving computing resources of devices associatedwith completing a transaction that would otherwise be consumed due to amismatch in verification methods associated with a transaction card andthe different locations, different merchants, and/or the like.

Although some implementations may be described in the context of an EMVtransaction (e.g., a transaction completed via an EMV chip), theimplementations apply equally to other types of transactions, such astransactions that use wireless communications to complete thetransactions (e.g., NFC transactions).

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may refer to a value beinggreater than the threshold, more than the threshold, higher than thethreshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, or the like.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A device, comprising: one or more memories; andone or more processors, communicatively coupled to the one or morememories, to: receive user input indicating that a modification to averification method associated with a transaction card from a firstverification method to a second verification method is approved, thefirst verification method and the second verification method usingdifferent types of verification information, the transaction card beingseparate from the device; determine that the verification methodassociated with the transaction card is to be modified based onreceiving the user input indicating that the modification to theverification method is approved, provide a set of instructions to thetransaction card after determining that the verification method is to bemodified, the set of instructions to cause the transaction card tomodify the verification method from the first verification method to thesecond verification method; and provide information identifying themodification to the verification method to a transaction backend deviceto notify the transaction backend device that the verification methodassociated with the transaction card has been modified from the firstverification method to the second verification method.
 2. The device ofclaim 1, where the first verification method is one of: a chip andpersonal identification number (PIN) method, or a chip and signaturemethod; and where the second verification method is the other of: thechip and PIN method, or the chip and signature method.
 3. The device ofclaim 1, where the one or more processors are further to: detect ageographic location of the device or the transaction card; and where theone or more processors, when determining that the verification method isto be modified, are to: determine that the verification method is to bemodified based on the geographic location of the device or thetransaction card, a first geographic location being associated with thefirst verification method, and a second geographic location beingassociated with the second verification method.
 4. The device of claim1, where the one or more processors, when determining that theverification method is to be modified, are to: determine that theverification method is to be modified based on one or more of:information indicating that the second verification method is associatedwith a geographic location of the device or the transaction card, orinformation indicating that an account associated with the device haspermission to modify the verification method.
 5. The device of claim 1,where the set of instructions are provided to the transaction card via:a wireless connection between the transaction card and the device, orthe transaction backend device.
 6. The device of claim 1, where the oneor more processors are further to: receive information identifying alocation of the device or the transaction card; identify the secondverification method, from multiple possible verification methods, to beconfigured for the transaction card based on the location of the deviceor the transaction card; and where the one or more processors, whenproviding the set of instructions, are to: provide the set ofinstructions to cause the second verification method to be configuredfor the transaction card based on identifying the second verificationmethod.
 7. The device of claim 1, where the one or more processors arefurther to: provide authentication information to the transactionbackend device to permit the set of instructions to modify theverification method.
 8. A non-transitory computer-readable mediumstoring instructions, the instructions comprising: one or moreinstructions that, when executed by one or more processors of a device,cause the one or more processors to: receive user input indicating thata modification to a verification method associated with a transactioncard from a first verification method to a second verification method isapproved, the first verification method and the second verificationmethod using different types of verification information, thetransaction card being separate from the device; determine that theverification method, is to be reconfigured from the first verificationmethod to the second verification method based on receiving the userinput indicating that the modification to the verification method isapproved, the second verification method including: a chip and personalidentification number (PIN) method, or a chip and signature method;provide a set of instructions to the transaction card to cause thetransaction card to reconfigure from the first verification method tothe second verification method, the set of instructions being providedto the transaction card via: a wireless connection between thetransaction card and a the device associated with the transaction card,or a transaction backend device; and provide information to thetransaction backend device to notify the transaction backend device thatthe verification method has been reconfigured to the second verificationmethod.
 9. The non-transitory computer-readable medium of claim 8, wherethe one or more instructions, when executed by the one or moreprocessors, further cause the one or more processors to: determinewhether the transaction card is within communicative proximity of thedevice associated with the transaction card; and where the one or moreinstructions, that cause the one or more processors to provide the setof instructions, cause the one or more processors to: provide the set ofinstructions to the transaction card via the wireless connection whenthe transaction card is within communicative proximity of the device, orprovide the set of instructions to the transaction card via thetransaction backend device when the transaction card is not withincommunicative proximity of the device.
 10. The non-transitorycomputer-readable medium of claim 8, where the one or more instructions,when executed by the one or more processors, further cause the one ormore processors to: provide authentication information to thetransaction backend device to permit the set of instructions to modifythe verification method.
 11. The non-transitory computer-readable mediumof claim 8, where the one or more instructions, that cause the one ormore processors to determine that the verification method is to bemodified, cause the one or more processors to: determine that theverification method is to be modified based on information identifying auser preference of a user of the device associated with the transactioncard, wherein the user preference prioritizes the second verificationmethod over another verification method.
 12. The non-transitorycomputer-readable medium of claim 8, where the one or more instructions,when executed by the one or more processors, further cause the one ormore processors to: prevent the set of instructions from being provideduntil the transaction card is within communicative proximity of thedevice.
 13. The non-transitory computer-readable medium of claim 8,where the one or more instructions, that cause the one or moreprocessors to determine that the verification method is to be modified,cause the one or more processors to: determine that the verificationmethod is to be modified based upon information indicating that anaccount associated with the device has permission to modify theverification method.
 14. A method, comprising: receiving, by a device,user input indicating that a modification to a verification methodassociated with a transaction card from a first verification method to asecond verification method is approved, the first verification methodand the second verification method using different types of verificationinformation, the transaction card being separate from the device;determining, by the device, that the verification method, is to bemodified based on receiving the user input indicating that themodification to the verification method is approved; providing, by thedevice, a set of instructions to the transaction card to cause thetransaction card to reconfigure from the first verification method tothe second verification method; and providing, by the device,information to a transaction backend device to notify the transactionbackend device that the verification method associated with thetransaction card has been modified from the first verification method tothe second verification method.
 15. The method of claim 14, wheredetermining that the verification method is to be modified comprises:determining that the verification method is to be modified based onreceiving transaction terminal information from the transaction cardwhen the transaction card is communicatively coupled to a transactionterminal.
 16. The method of claim 14, where determining that theverification method is to be modified comprises: determining that theverification method is to be modified based on receiving transactionbackend information from the transaction backend device when thetransaction card is used to complete a transaction.
 17. The method ofclaim 14, where the verification method includes: a chip and personalidentification number (PIN) method, a chip and signature method, or abiometric verification method.
 18. The method of claim 14, where the setof instructions cause the transaction card to disable the verificationmethod and enable a different verification method.
 19. The method ofclaim 14, where determining that the verification method is to bemodified comprises: determining that the verification method is to bemodified based on a request from the transaction card to modify theverification method.
 20. The method of claim 14, further comprising:providing authentication information to the transaction backend deviceto permit the set of instructions to modify the verification method.